Critical: seamonkey security update
Security Advisory: Critical
Updated seamonkey packages that fix several security issues are now
available for Red Hat Enterprise Linux 3 and 4.
The Red Hat Security Response Team has rated this update as having critical
security impact. Common Vulnerability Scoring System (CVSS) base scores,
which give detailed severity ratings, are available for each vulnerability
from the CVE links in the References section.
SeaMonkey is an open source web browser, email and newsgroup client, IRC
chat client, and HTML editor.
Several flaws were found in the processing of malformed web content. A web
page containing malicious content could cause SeaMonkey to crash or,
potentially, execute arbitrary code with the privileges of the user running
SeaMonkey. (CVE-2010-1211, CVE-2010-2753, CVE-2010-1214)
A memory corruption flaw was found in the way SeaMonkey decoded certain PNG
images. An attacker could create a specially-crafted PNG image that, when
opened, could cause SeaMonkey to crash or, potentially, execute arbitrary
code with the privileges of the user running SeaMonkey. (CVE-2010-1205)
A same-origin policy bypass flaw was found in SeaMonkey. An attacker could
create a malicious web page that, when viewed by a victim, could steal
private data from a different website the victim has loaded with SeaMonkey.
(CVE-2010-2754)
A flaw was found in the way SeaMonkey displayed the location bar when
visiting a secure web page. A malicious server could use this flaw to
present data that appears to originate from a secure server, even though it
does not. (CVE-2010-2751)
All SeaMonkey users should upgrade to these updated packages, which correct
these issues. After installing the update, SeaMonkey must be restarted for
the changes to take effect.
Before applying this update, make sure all previously-released errata
relevant to your system have been applied.
This update is available via the Red Hat Network. Details on how to
use the Red Hat Network to apply this update are available at
http://kbase.redhat.com/faq/docs/DOC-11259
Vulmon